This will be used on the wrapping components to determing timing as to when it will next display.  Guessing we will also have to add progression logic here… like number of ansered vs total.

Meaning postal code wont be asked unless country code is us, canada or mexico or other address related logic like region code is also not able to be asked based on country.

Everything is required when visible.  Also update address field logic so that only the postalCode & regionCode fields are dependent on countryCode bein answered.

Also add visible logic to consent input in oreder to display when not answered.

Add requiresPUI(progressive user input) and validation on the identityX access service call.  this will allow us to add to the identityX access check on content landing pages in order to use progressive reg on content gate.

Initial port from profile components and routes as it will have to support the same variation of inputs.  It does have added logic to only display one question at the moment based on array of configured ids.

example: [ givenName, familyName, phone, 618a8a62934f8400ad4beb8f]

It will only display on unanswered question in order at the moment.